Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1518

reference: 852-tree-1
name: 1518
tree-preservation-order: undefined
852-tpo-1
uprn
address-text
point: POINT (-0.969144 50.864929)
geometry: MULTIPOLYGON (((-0.969073 50.864922,-0.969076 50.864936,-0.969086 50.864948,-0.969101 50.864958,-0.969121 50.864965,-0.969143 50.864967,-0.969165 50.864965,-0.969185 50.864959,-0.969201 50.864949,-0.969211 50.864937,-0.969215 50.864923,-0.969212 50.864909,-0.969202 50.864897,-0.969186 50.864886,-0.969167 50.864880,-0.969145 50.864877,-0.969123 50.864879,-0.969103 50.864886,-0.969087 50.864895,-0.969076 50.864908,-0.969073 50.864922)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL